Loop the teaser - #68
Merged
Merged
Conversation
The video autoplays muted in a loop, with controls kept and autoplay removed under prefers-reduced-motion. Decision 19 records why the YouTube nocookie embed was rejected and what autoplay does to the bandwidth math. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Internal discussion concluded the teaser should always be running: the ink only reads in motion, and a poster frame sells a still image. The video element now autoplays muted in a loop. Controls stay visible so the loop remains pausable, and a small script removes the autoplay for visitors whose system asks for reduced motion — they get the poster and a play button.
A YouTube nocookie embed was considered for this and rejected: privacy-enhanced mode only defers cookies until playback, and an autoplaying loop triggers playback on page load for every visitor, so the no-cookie claim would not survive. It would also reintroduce the region-blocking and third-party problems decision 19 removed.
The cost that changes is bandwidth: every home-page visit now downloads a rendition (~3 MB), which puts GitHub Pages'' ~100 GB/month soft limit at roughly 30,000 visits a month. Decision 19 is amended with the loop, the rejection reasoning, and the escape hatch if traffic ever gets there.
🤖 Generated with Claude Code